Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference
468-tree-1
name
1662
tree-preservation-order

undefined

468-tpo-1
uprn
address-text
point
POINT (-1.023896 50.882710)
geometry
MULTIPOLYGON (((-1.023826 50.882702,-1.023829 50.882716,-1.023839 50.882729,-1.023854 50.882739,-1.023874 50.882745,-1.023896 50.882748,-1.023918 50.882746,-1.023938 50.882739,-1.023954 50.882730,-1.023964 50.882717,-1.023968 50.882703,-1.023964 50.882689,-1.023955 50.882677,-1.023939 50.882667,-1.023919 50.882660,-1.023898 50.882658,-1.023876 50.882660,-1.023856 50.882666,-1.023840 50.882676,-1.023829 50.882688,-1.023826 50.882702)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL